SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Secure messaging</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Secure messaging</span></span>

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style>

<p><b>Secure messaging</b><sup id="cite_ref-:0_1-0" class="reference"><a href="#cite_note-:0-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> is a server-based approach to protect sensitive data when sent beyond the corporate borders, and it provides compliance with industry regulations such as <a href="HIPAA" class="mw-redirect" title="HIPAA">HIPAA</a>, <a href="GLBA" class="mw-redirect" title="GLBA">GLBA</a> and <a href="Sarbanes%E2%80%93Oxley_Act" title="Sarbanes–Oxley Act">SOX</a>. Advantages over classical secure e-mail are that confidential and <a href="Authentication" title="Authentication">authenticated</a> exchanges can be started immediately by any internet user worldwide since there is no requirement to install any <a href="Software" title="Software">software</a> nor to obtain or to distribute <a href="Key_(cryptography)" title="Key (cryptography)">cryptographic keys</a> beforehand. Secure messages provide non-repudiation as the recipients (similar to <a href="Online_banking" title="Online banking">online banking</a>) are personally identified and transactions are logged by the secure email platform.<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Functionality">Functionality</h2></div>

<p>Secure messaging works as an online messaging service. Firstly, users enroll in a secure messaging platform. Then, the user logs into their account by typing in their <a href="User_(computing)" title="User (computing)">username</a> and <a href="Password" title="Password">password</a> (or strong authentication) similar to a web-based email account. Out of a message center, the messages can be sent over a <a href="Transport_Layer_Security" title="Transport Layer Security">secure SSL-connection</a> or via other equally protecting methods to any recipient. If the recipient is contacted for the first time, a message unlock code <a href="#MUC_(message_unlock_code)">(see below MUC)</a> is needed to authenticate the recipient. Alternatively, secure messaging can be used out of any standard email program without installing software.<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Secure_delivery">Secure delivery</h2></div>

<p>Secure messaging possesses different types of delivery: secured web interface, <a href="S/MIME" title="S/MIME">S/MIME</a> or <a href="Pretty_Good_Privacy" title="Pretty Good Privacy">PGP</a> encrypted communication or <a href="Transport_Layer_Security" title="Transport Layer Security">TLS</a> secured connections to email domains, or individual email clients. One single secure message can be sent to different recipients with different types of secure delivery that the sender does not have to worry about.

</p>

<div class="mw-heading mw-heading2"><h2 id="Trust_management">Trust management</h2></div>

<p>Secure messaging relies on a <a href="Web_of_trust" title="Web of trust">web of trust</a>. This method synthesizes the authentication approach of web of trust, known from <a href="Pretty_Good_Privacy" title="Pretty Good Privacy">PGP</a>, with the advantages of hierarchical structures, known from centralized <a href="Public_key_infrastructure" title="Public key infrastructure">PKI systems</a>.<sup id="cite_ref-:0_1-1" class="reference"><a href="#cite_note-:0-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> Those combined with certificates provide a high quality of electronic identities. This approach focuses on the user and allows for immediate and personal bootstrapping of trust, respectively revocation.

</p>

<div class="mw-heading mw-heading2"><h2 id="Physical_security">Physical security</h2></div>

<p>In a traditional client-server email, message data is downloaded to a local hard drive, and it is vulnerable if the computer is lost, stolen, or physically accessed by an unauthorized person. Secure messages are stored on a network or internet server which are typically more physically secure, and they are encrypted when data is inbound or outbound. However, an abundance of data still makes the server an attractive target for remote attacks. Methods that can be taken to protect physical security include ensuring environmental safety and hardware safety.<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> Of course, the intentions of the server operator may also come into question.

</p>

<div class="mw-heading mw-heading2"><h2 id="Application">Application</h2></div>

<p>Secure messaging is used in many business areas with company-wide and sensitive data exchanges. Financial institutions, insurance companies, public services, health organizations, and service providers rely on the protection from secure messaging. Secure messaging can be easily integrated into corporate email infrastructures.<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup> According to Wolcott et al., secure messaging offers potential improvements in patient-provider relationships and outcomes.<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup>

</p><p>In the government context, secure messaging can offer electronic <a href="Registered_mail" title="Registered mail">registered mail</a> functions. For this to be binding, some countries, such as Switzerland,<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> require it to be accredited as a secure platform.

</p>

<div class="mw-heading mw-heading2"><h2 id="Technical_requirements">Technical requirements</h2></div>

<p>There is no software required for using Secure messaging. Users only need a valid email address and a working internet connection with an up-to-date <a href="Web_browser" title="Web browser">web browser</a>.

</p>

<div class="mw-heading mw-heading2"><h2 id="User_impact">User impact</h2></div>

<p>With its use in business areas and one-on-one interaction secure messaging for recipients also includes their desire to share information with another party and negotiating the different rules across state borders. Even with the private misuse of some information data, some recipients continue to use the service. This may be referred to as a privacy paradox, where convenience of usage in apps such as secure messaging may be more important than the privacy concern in information systems.<sup id="cite_ref-8" class="reference"><a href="#cite_note-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Similar_technologies">Similar technologies</h2></div>

<li><a href="Identity-Based_Encryption" class="mw-redirect" title="Identity-Based Encryption">Identity-Based Encryption</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

<ul><li>1965: <a href="Mainframe_computer" title="Mainframe computer">Mainframe computer</a> users are able to exchange messages.</li>

<li>1982: Standard for (D)ARPA internet text messages (RFC822) is adopted: different email systems can communicate with each other.</li>

<li>1983: Development of the <a href="Internet_Protocol" title="Internet Protocol">Internet Protocol</a></li>

<li>1991: <a href="Phil_Zimmermann" title="Phil Zimmermann">Phil Zimmermann</a> creates PGP in 1991, a first-generation for secure mail communication.</li>

<li>1999: Launch of browser-based internet banking at <a href="UBS_AG" class="mw-redirect" title="UBS AG">UBS AG</a> (Union Bank of Switzerland) with the advent of strong cryptography in industry standard browsers.</li>

<li>2001: <a href="Google" title="Google">Google</a> <a href="Search_engine" title="Search engine">search engine</a> indexes more than 1 billion internet pages: cooperating web sites can be found easily</li>

<li>2002: Introduction of strong <a href="Authentication" title="Authentication">authentication</a> in internet banking (UBS Switzerland) to prevent identity fraud.</li>

<li>2005: More than 1 billion internet users: most people in industrial countries can be reached via the internet</li></ul>

<ul><li><a href="Information_security" title="Information security">Information security</a></li>

<li><a href="Email_authentication" title="Email authentication">Email authentication</a></li>

<li><a href="Email_encryption" title="Email encryption">Email encryption</a></li>

<li><a href="Email_privacy" title="Email privacy">Email privacy</a></li>

<li><a href="Secure_communication" title="Secure communication">Secure communication</a></li>

<li><a href="Secure_instant_messaging" class="mw-redirect" title="Secure instant messaging">Secure instant messaging</a></li>

<li><a href="Transport_Layer_Security" title="Transport Layer Security">Transport Layer Security</a></li>

<li><a href="Cryptography" title="Cryptography">Cryptography</a></li>

<li><a href="Electronic_signature" title="Electronic signature">Electronic signature</a></li>

<li><a href="Certified_email" title="Certified email">Certified email</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://fortricks.in/is-your-text-messages-are-secure/">"secure-messaging"</a>. 29 August 2023.</cite></span>

</li>

<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text"><cite id="CITEREFMENAFN" class="citation web cs1">MENAFN. <a rel="nofollow" class="external text" href="https://menafn.com/1101000084/Secure-Messaging-in-Healthcare-Market-Innovations-Trends-Technology-And-Applications-Market-Report-To-2020-2025">"Secure Messaging in Healthcare Market Innovations, Trends, Technology And Applications Market Report To 2020-2025"</a>. <i>menafn.com</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2020-10-23</span></span>.</cite></span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://help.secure-messaging.com/apps-add-ins-extensions/outlook-add-in/">"Outlook Add-in | Secure Messaging"</a>. <i>help.secure-messaging.com</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2020-11-12</span></span>.</cite></span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://flylib.com/books/en/4.446.1.41/1/">"Beefing Up Your Physical Security | Secure Messaging with Microsoft Exchange Server 2000"</a>. <i>flylib.com</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2021-04-20</span></span>.</cite></span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><cite id="CITEREFGruber" class="citation journal cs1">Gruber, Tom. "Enterprise Collaboration Management with Intraspect". <i>Intraspect Technical White Paper</i>.</cite></span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><cite id="CITEREFWolcottAgarwalNelson2017" class="citation journal cs1">Wolcott, Vickee; Agarwal, Ritu; Nelson, D. Alan (2017-04-06). <a rel="nofollow" class="external text" href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5399218">"Is Provider Secure Messaging Associated With Patient Messaging Behavior? Evidence From the US Army"</a>. <i>Journal of Medical Internet Research</i>. <b>19</b> (4): e103. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.2196%2Fjmir.6804">10.2196/jmir.6804</a></span>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1438-8871">1438-8871</a>. <a href="PMC_(identifier)" class="mw-redirect" title="PMC (identifier)">PMC</a> <span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5399218">5399218</a></span>. <a href="PMID_(identifier)" class="mw-redirect" title="PMID (identifier)">PMID</a> <a rel="nofollow" class="external text" href="https://pubmed.ncbi.nlm.nih.gov/28385681">28385681</a>.</cite></span>

</li>

<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20110706221208/http://www.isb.admin.ch/themen/sicherheit/00530/01200/index.html?lang=en">"FSUIT - Electronic delivery platforms"</a>. <i>www.isb.admin.ch</i>. Archived from <a rel="nofollow" class="external text" href="http://www.isb.admin.ch/themen/sicherheit/00530/01200/index.html?lang=en">the original</a> on 2011-07-06.</cite> </span>

</li>

<li id="cite_note-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-8">^</a></b></span> <span class="reference-text"><cite id="CITEREFBélangerCrossler2011" class="citation journal cs1">Bélanger, France; Crossler, Robert E. (2011). "Privacy in the Digital Age: A Review of Information Privacy Research in Information Systems". <i>MIS Quarterly</i>. <b>35</b> (4): <span class="nowrap">1017–</span>41. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.2307%2F41409971">10.2307/41409971</a>. <a href="Hdl_(identifier)" class="mw-redirect" title="Hdl (identifier)">hdl</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://hdl.handle.net/10919%2F81984">10919/81984</a></span>. <a href="JSTOR_(identifier)" class="mw-redirect" title="JSTOR (identifier)">JSTOR</a> <a rel="nofollow" class="external text" href="https://www.jstor.org/stable/41409971">41409971</a>.</cite></span>

</li>

</ol></div></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2024-07-29" href="https://en.wikipedia.org/wiki/?title=Secure_messaging&oldid=1237465792">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>